feat: Added deploy script for checking deployments #738
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ailisp
reviewed
Jul 29, 2024
|
|
||
| let status = status.await?; | ||
| dbg!(&status); | ||
| assert!(status.is_failure(), "expected to timeout"); |
There was a problem hiding this comment.
Is it possible fail due to deserialize certain state failed (caused by migration)? Should we check execution outcome fail reason
There was a problem hiding this comment.
yeah, it's possible to fail, which is why this script just checks if we can do a migration. The dbg!(&status) will show us the cause of the migration failing
|
I added in CI checks for doing this deploy check. Just do the init_running for dev for now when you guys get the chance |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now we can check whether or not our deployments are going to break state for contracts or not.
You can check against dev by running:
cargo test -- run_dev --show-output